50 years of isolation

The traditional means for isolating applications from each other is via the use of operating system provided “process” abstraction facilities. However, as applications now consist of multiple fine-grained components, the traditional process abstraction model is proving to be insufficient in ensuring this isolation. Statistics indicate that a high percentage of software failure occurs due to propagation of component failures. These observations are further bolstered by the attempts by modern Internet browser application developers, for example, to adopt multi-process architectures in order to increase robustness. Therefore, a fresh look at the available options for isolating program components is necessary and this paper provides an overview of previous and current research on the area

Design and implementation of unified communications as a service based on the OpenStack cloud environment

Cloud Computing, based on early virtual computer concepts and technologies, is now itself a maturing technology in the marketplace and it has revolutionized the IT industry, being the powerful platform that many businesses are choosing to migrate their in-premises IT services onto. Cloud solution has the potential to reduce the capital and operational expenses associated with deploying IT services on their own. In this study, we have implemented our own private cloud solution, infrastructure as a service (IaaS), using the OpenStack platform with high availability and a dynamic resource allocation mechanism. Besides, we have hosted unified communication as a service (UCaaS) in the underlying IaaS and successfully tested voice over IP (VoIP), video conferencing, voice mail and instant messaging (IM) with clients located at the remote site. The proposed solution has been developed in order to give advice to bussinesses that want to build their own cloud environment, IaaS and host cloud services and applicatons in the cloud. This paper also aims at providing an alternate option for proprietary cloud solutions for service providers to consider

Design, implementation and evaluation of unified communications on-premises and over the Cloud

Unified Communication (UC) is the integration of two or more real time communication systems into one platform. Integrating core communication systems into one overall enterprise level system delivers more than just cost saving. These real-time interactive communication services and applications over Internet Protocol (IP) have become critical in boosting employee accessibility and efficiency, improving customer support and fostering business agility. However, some small and medium-sized businesses (SMBs) are far from implementing this solution due to the high cost of initial deployment and ongoing support. Cloud based UC solution, UC as a Service (UCaaS), is now itself a maturing technology in the marketplace and it has revolutionized the IT industry, being the powerful platform that many businesses are choosing to migrate their on-premises UC solution onto. UCaaS solution has the potential to reduce the capital and operational expenses associated with deploying UC on their own. In this paper, we will discuss and demonstrate an open source on-premises UC solution, viz. “Asterisk” for use by businesses, and report on some performance tests using SIPp. This paper also discusses and demonstrates an open source UCaaS solution. The contribution from this research is the provision of technical advice to businesses in deploying UC and UCaaS, which is manageable in terms of cost, ease of deployment and support

Response to The Department of the Prime Minister and Cabinet's discussion paper "Connecting with Confidence"

The ACS has prepared this response to the discussion paper to assist with the design of the cyber whitepaper expected in 2012. The ACS also welcomes the opportunity to promote discussion and support of our digital economy to position Australia for the future. Drawing from its membership of ICT professionals, and academics - particularly in areas of cyber resilience and security - the ACS established a Cyber Taskforce for this purpose. The ACS recommends: greater focus on education - noting that ICT education in primary and secondary schooling is essential - to developing ICT skills of the future and that school level educational activity forms the base on which appropriate tertiary level education programs can function for the education and training of ICT professionals; greater assistance to small and medium sized business as this is the engine room of the Australian economy; policy coordination on trusted identities; better coordination of cyber related education and research; providing consumers and businesses with resources directed to the everyday real-life challenges they face; global Internet governance changes designed to underpin and deliver trustworthy people, processes and systems including, where appropriate, a legislated mandatory baseline of trustworthiness attributes analogous to the non-excludable warranties implied in consumer contacts

A definition of flare in low back pain (LBP): A multiphase process involving perspectives of individuals with LBP and expert consensus

Low back pain (LBP) varies over time. Consumers, clinicians and researchers use various terms to describe fluctuations of LBP symptoms. Although "flare" is commonly used to describe symptom fluctuation, there is no consensus on how it is defined. This study aimed to obtain consensus for a LBP flare definition using a mixed-method approach. Step 1 involved derivation of a preliminary candidate flare definition based on thematic analysis of consumers' views in consultation with an expert consumer writer. In Step 2, a workshop was conducted to incorporate perspectives of LBP experts into the preliminary flare definition, which resulted in two alternative LBP flare definitions. Step 3 refined the definition using a two-round Delphi consensus process with experts in musculoskeletal conditions. The definition favoured by experts was further tested with individuals with LBP in Step 4, using the definition in three scenarios. This multiphase study produced a LBP flare definition that distinguishes it from other LBP fluctuations, represents views of consumers, involves expert consensus, and is understandable by consumers in clinical and research contexts: "A flare-up is a worsening of your condition that lasts from hours to weeks that is difficult to tolerate and generally impacts your usual activities and/or emotions". Perspective: A multiphase processes produced a low back pain (LBP) flare definition that distinguishes it from other LBP fluctuations, involves expert consensus and represents consumers' views

Background to the development of a curriculum for the history of 'cyber' and 'communications' security

For any discipline to be regarded as a professional undertaking by which its members may be treated as true “professionals” in a specific area, practitioners must clearly understand that discipline’s history as well as the place and significance of that history in current practice as well as its relevance to available technologies and artefacts at the time. This is common for many professional disciplines such as medicine, pharmacy, engineering, law and so on but not yet, this paper submits, in information technology. Based on twenty five elapsed years of experience in developing and delivering Cybersecurity courses at undergraduate and postgraduate levels, this paper proposes a rationale and set of differing perspectives for the planning and development of curricula relevant to the delivery of appropriate courses in the history of cybersecurity or information assurance to information and communications technology (ICT) students and thus to potential information technology professionals

Open Trusted Health Informatics Structure (OTHIS)

The potential for development and deployment of trusted health information systems (HIS) based upon intrinsically more secure computer system architectures than those in general use, as commodity level systems, in today's marketplace is investigated in this paper. A proposal is made for a viable, trusted architecture for HIS, entitled the “Open Trusted Health Informatics Structure (OTHIS)”, based upon a set of separate but connected trusted modules. OTHIS addresses privacy and security requirements at all levels in an HIS. In this paper, we are concerned with the role of trustworthy access control mechanisms in HIS architectures. Our proposed OTHIS architecture gives direction on how trustworthiness in HIS can be achieved

A test vehicle for compliance with resilience requirements in index-based e-health systems

Increasingly, national and international governments have a strong mandate to develop national e-health systems to enable delivery of much-needed healthcare services. Research is, therefore, needed into appropriate security and reliance structures for the development of health information systems which must be compliant with governmental and alike obligations. The protection of e-health information security is critical to the successful implementation of any e-health initiative. To address this, this paper proposes a security architecture for index-based e-health environments, according to the broad outline of Australia’s National E-health Strategy and National E-health Transition Authority (NEHTA)’s Connectivity Architecture. This proposal, however, could be equally applied to any distributed, index-based health information system involving referencing to disparate health information systems. The practicality of the proposed security architecture is supported through an experimental demonstration. This successful prototype completion demonstrates the comprehensibility of the proposed architecture, and the clarity and feasibility of system specifications, in enabling ready development of such a system. This test vehicle has also indicated a number of parameters that need to be considered in any national indexed-based e-health system design with reasonable levels of system security. This paper has identified the need for evaluation of the levels of education, training, and expertise required to create such a system

Mutual protection in a cloud computing environment

The term “cloud computing” has emerged as a major ICT trend and has been acknowledged by respected industry survey organizations as a key technology and market development theme for the industry and ICT users in 2010. However, one of the major challenges that faces the cloud computing concept and its global acceptance is how to secure and protect the data and processes that are the property of the user. The security of the cloud computing environment is a new research area requiring further development by both the academic and industrial research communities. Today, there are many diverse and uncoordinated efforts underway to address security issues in cloud computing and, especially, the identity management issues. This paper introduces an architecture for a new approach to necessary “mutual protection” in the cloud computing environment, based upon a concept of mutual trust and the specification of definable profiles in vector matrix form. The architecture aims to achieve better, more generic and flexible authentication, authorization and control, based on a concept of mutuality, within that cloud computing environment

Performance analysis of secure unified communications in the VMware-based cloud

Unified communications as a service (UCaaS) can be regarded as a cost-effective model for on-demand delivery of unified communications services in the cloud. However, addressing security concerns has been seen as the biggest challenge to the adoption of IT services in the cloud. This study set up a cloud system via VMware suite to emulate hosting unified communications (UC), the integration of two or more real time communication systems, services in the cloud in a laboratory environment. An Internet Protocol Security (IPSec) gateway was also set up to support network-level security for UCaaS against possible security exposures. This study was aimed at analysis of an implementation of UCaaS over IPSec and evaluation of the latency of encrypted UC traffic while protecting that traffic. Our test results show no latency while IPSec is implemented with a G.711 audio codec. However, the performance of the G.722 audio codec with an IPSec implementation affects the overall performance of the UC server. These results give technical advice and guidance to those involved in security controls in UC security on premises as well as in the cloud